Updates Your Manager Actually Reads
Tuesday, 9:12 am. John is eight months into a support analyst job. He sends this to his team lead:
"Hi, still working on the refund report. Almost done. Will update you."
She opens it, closes it, moves on. No reply.
Same report, second version:
"Refund report is 80% done, ready by 3pm. March has 41 duplicate rows.
I can drop them or keep them flagged. Which do you prefer?"
She replied in four minutes.
The second message gave her something to do
The first message says John is busy. She already assumed that. The second one hands her a choice she can make in ten seconds.
Team leads read a stack of these before their first meeting. Belal Zahran, in a guide to standup updates managers actually read, says they scan 8 to 15 updates each morning. They are checking two things: what is at risk, and who needs help.
A message that answers neither gets skimmed. Not because she does not care. At 9:12 am she has eleven of them open and a status call at 9:30.
There is a second reason the first version failed. An article on why bosses seem harder to read than they are by Mira Ranjan explains this beautifully. She splits managers into headline people and detail people.
- Headline people want the conclusion first. Bury your point at the bottom of three paragraphs, and they stop reading at line two.
- Detail-oriented people want the row count.
John's second message works for both. The headline person gets the deadline and the question. The detail person gets the 41 rows.
He did not write more. He wrote the same forty words in a better order. The choice sits where her eye lands last.
The whole idea is that an update earns a reply when it ends with something your manager can decide.
The four lines
Four lines. Nothing under them. Copy this shape:
- Status: what is done, in numbers.
- Next: what you are doing now, with a time on it.
- Risk: what could slow it down, or the word "none."
- Ask: the decision you need, or "nothing needed."
John's version looked like this:
- Status: Refund report 80% done. Found 41 duplicate rows in March.
- Next: Running final checks, ready by 3pm.
- Risk: Keeping the duplicates puts the total off by about 4%.
- Ask: Drop them or flag them?
Two rules keep this working. Every line carries a number, a name, or a time. And Ask stays at the bottom, because that is the line she remembers when the meeting starts.
Liz Christo answered a reader question on keeping your manager updated with the same move. Hand over the problem with the options already attached.
"Do you have a preference?" gets an answer. "What should I do?" gets silence and a longer meeting later.
When to send it
Timing is equally important, though.
- Monday before 10am: your priorities for the week, plus anything you need a decision on. Keep it under six lines.
- Midweek: only when something changes. A new risk, a date that slipped, a choice you cannot make alone. Otherwise, stay quiet.
- Friday before you log off: what closed, what moved, and what is still open.
- Anything that will surprise her: send it the same hour you learn it. She should never hear your bad news from someone else.
Write the update at the end of your day. At 5pm you still remember the row count and the file name. At 9am you write "worked on the report" and lose the whole thing.
Give yourself six minutes for it, in a calendar block if that helps. Six minutes on Monday buys back the twenty-minute call on Thursday where she asks where everything stands.
The week you have nothing to report
Silence reads like avoidance. Send it anyway, and be exact about why nothing moved.
- Weak: "No update this week, still waiting."
- Better: "Vendor list is still blocked. I emailed Rina Monday and Wednesday; no reply. Can you nudge her, or should I move to the backup?"
Blocked is real information. Name who you are waiting on, what you already tried, and the date it started.
Then attach the ask. She has one thing you do not: the standing to chase Rina without it being awkward.
A stalled week with a clear owner and a date is easier to read than a vague, busy one. She can act on the first. She can only worry about the second.
Small swaps that change your reply rate
"Working on the deck" becomes "Deck is at 6 slides of 10, draft by Thursday."
"Almost done" becomes "Two hours left; sending by 2pm."
"There's an issue" becomes "The export fails on files over 50MB. I can split it. Okay?"
"No blockers" becomes "Waiting on the design specs. Pinged Sarah Monday, nothing yet."
"Let me know your thoughts" becomes "Option A or B? I will go with A if I hear nothing by Friday."
The last one does the most work. A stated default lets a busy manager approve by saying nothing at all.
Use it for anything reversible. Keep the open question for the calls you cannot take back on your own.
Try it on one message today
Take a message you were going to send this afternoon. Rewrite it in the four lines. Send it.
Do it again tomorrow, and again on Thursday. Three attempts is enough to feel the shape without thinking about it.
You will see which line gets answered fastest by Friday . Usually it is the "ask" line, because answering it costs her four seconds and one word.
John still sends the same number of messages every week. Each one now ends with a question his lead can answer in a word. Three weeks in, she started replying to him before anyone else on the team.
